System and method of direct write and mapping of data in a non-volatile memory having multiple sub-drives

ABSTRACT

A system and method is disclosed for managing data in a non-volatile memory. The system may include a non-volatile memory having multiple non-volatile memory sub-drives. A controller of the memory system is configured to route incoming host data to a desired sub-drive, keep data within the same sub-drive as its source during a garbage collection operation, and re-map data between sub-drives, separate from any garbage collection operation, when a sub-drive overflows its designated amount logical address space. The method may include initial data sorting of host writes into sub-drives based on any number of hot/cold sorting functions. In one implementation, the initial host write data sorting may be based on a host list of recently written blocks for each sub-drive and a second write to a logical address encompassed by the list may trigger routing the host write to a hotter sub-drive than the current sub-drive.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 16/554,527,filed on Aug. 28, 2019, now U.S. Pat. No. 11,016,882, which is acontinuation of application Ser. No. 15/954,171, filed on Apr. 16, 2018,now U.S. Pat. No. 10,409,720, which claims the benefit of U.S.Provisional Application No. 62/518,513, filed on Jun. 12, 2017, theentirety of each of which is herein incorporated by reference.

BACKGROUND

Storage systems, such as solid state drives (SSDs) including NAND flashmemory, are commonly used in electronic systems ranging from consumerproducts to enterprise-level computer systems. SSDs and similar storagedevices utilizing block-oriented architectures share a common issue: theneed to create space for writing new data by collecting sparselydistributed data into a smaller number of blocks. This process isreferred to as “garbage collection”. The need for garbage collection inmany block-oriented storage devices is generally due to the inability towrite in place to memory, and the mismatch between write granularity anderase granularity in those storage devices.

The garbage collection process may introduce a significant burden onprocessing resources which, in turn, may reduce SSD performance. Garbagecollection involves reading valid data from a block of non-volatilememory that is to be reused and writing it back to a new block. Manyreal-life data workloads, notably except uniform random and sequential,have different write densities for different logical areas, with somedata being ‘hot’ or frequently written, and ‘cold’ or less frequentlywritten. When data of different temperatures is mixed together, the SSDcan experience significant write amplification, where writeamplification refers to the physical amount of data written or copiedabove the logical amount of data received.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of an example non-volatile memory system.

FIG. 1B is a block diagram illustrating an exemplary storage module.

FIG. 1C is a block diagram illustrating a hierarchical storage system.

FIG. 2A is a block diagram illustrating exemplary components of acontroller of a non-volatile memory system.

FIG. 2B is a block diagram illustrating exemplary components of anon-volatile memory of a non-volatile memory storage system.

FIG. 3 illustrates an example physical memory organization of thenon-volatile memory system of FIG. 1A.

FIG. 4 shows an expanded view of a portion of the physical memory ofFIG. 3 .

FIG. 5 illustrates is an example of a physical superblock of thenon-volatile memory.

FIG. 6 is a block diagram of the non-volatile memory of FIG. 2A dividedin to multiple sub-drives.

FIG. 7 is a block diagram of the sub-drives of FIG. 6 arranged with aparticular logical space and workload distribution.

FIGS. 8A and 8B illustrate different data age tracking lists fortracking the temperature of super-blocks.

FIG. 8C is a legend of different entry types in the tracking lists ofFIGS. 8A and 8B.

FIGS. 9A and 9B illustrate a monitoring window of most recently receivedhost data that is used to determine current temperature of logicaladdresses in the non-volatile memory system.

FIG. 10 is a flow diagram illustrating one implementation of managingdata flow in a non-volatile memory such as shown in FIGS. 6-7 .

FIG. 11 is a flow diagram illustrating a process for determining thesub-drive in the non-volatile memory from which to select a source blockfor garbage collection and for then re-mapping valid superblocks betweensub-drives independently of a garbage collection operation.

FIG. 12 illustrates an alternative embodiment for initial host writedata sorting in the non-volatile memory of FIGS. 6-7 .

FIG. 13 is a hypothetical plot of responsiveness of sub-drives tochanging workload based on different hot host list size.

FIG. 14 is a flow diagram setting forth an embodiment of initial hostwrite data sorting to sub-drives based on a recent host write densitydetermination.

FIG. 15 illustrates an example write amplification surface usable todetermine an optimal write amplification point with which to setrelative target overprovisioning levels in multiple sub-drives.

DETAILED DESCRIPTION

In order to address write amplification issues, and to reduce datamanagement overhead burdens that can be created in addressing writeamplification issues, a system and method for managing data in anon-volatile memory (NVM) system having multiple sub-drives is disclosedbelow.

As described herein, write amplification issues that may occur in alegacy NVM system due to the mixture of different data groups, such asdifferent temperature data, may be addressed at several different pointsin the operation of the NVM system. For example, in one implementationthe method and system separates hot/cold data sorting from garbagecollection for data that has been already been written to a sub-drive.In another implementation that may be used in combination with, orindependently from the separated garbage collection and hot/cold datasorting noted above, the system and method may include an initial sortof data into a desired sub-drive as it is being written from the host.

Thus, aspects that may be usable separately or in combination mayinclude:

Direct Host Write Path

The NVM system may be configured to strive for an optimal direct writedata path to different sub-drives, where the host writes are directlyrouted to separate sub-drives assigned for specific data groups (e.g.,‘hot’ vs. ‘cold’) as the intended the final destination. The sub-drivedestination decision may be done ‘on-the-fly’, as the data is written bythe host, to obtain a direct write and avoid any penalty of anintermediate write that may require a subsequent sort. The host write ofa logical block address (LBA) or logical group may be made to anysub-drive.

Local Garbage Collection

Each sub-drive may have its own independent garbage collection so thatno data would move from one sub-drive to another unless resizing isrequired. This may avoid problems where data would otherwise bere-classified as ‘colder’ and get moved to another sub-drive justbecause other data in the block became obsolete and the block wasselected for reclaim (garbage collection) operation. As describedherein, the new free block generated by the garbage collection operationwould go into a shared free block pool and may be reused by either thesame sub-drive or a different sub-drive. In different embodiments, thesize of a sub-drive may either be fixed or change according to are-sizing algorithm if the workload changes.

Passive Super-Block Re-Assignment.

If sub-drive re-sizing is triggered, it may be accomplished by makingsub-drives smaller via re-assigning the ‘coldest’ super-block to a‘colder’ sub-drive, for example, the next ‘colder’ sub-drive. The‘coldest’ super-blocks may be moved between sub-drives withoutphysically copying data from one sub-drive to another to avoid a writeamplification penalty. As described below, the least recently writtenblock may be identified as containing the ‘coldest’ data in theparticular sub-drive. For each sub-drive, the write order of superblocksby the host may be maintained as a basis to determine the temperature ofthe superblocks.

Overprovisioning Management

As described in greater detail below, the overprovisioning (OP) targetsfor each sub-drive may be based on a workload analysis for eachsub-drive. The workload analysis may be used for calculations of OP,sub-drive sizes and/or data routing and may be based on tracking hitrate per sub-drive, based on the current data location. The target OP ofeach sub-drive may be determined from the workload analysis and then beused to determine from which sub-drive a source superblock should beselected for garbage collection.

According to a first aspect, a method for managing data in a memorysystem is disclosed. The method may be executed with a controller incommunication with a non-volatile memory having a plurality ofsub-drives. The method may include the controller receiving a host datawrite at the memory system and directing the host data write to one ofthe plurality of sub-drives based on a first sorting technique. Themethod may also include initiating a garbage collection operation in aparticular sub-drive in response to a detected garbage collectiontrigger and moving valid data during the garbage collection operationfrom a source superblock in the particular sub-drive only to arelocation superblock in the particular sub-drive such that the validdata remains in the particular sub-drive. Additionally, the method mayinclude determining whether a proportion of a total logical addressspace of the non-volatile memory currently associated with one of theplurality of sub-drives exceeds a predetermined threshold. When theproportion exceeds the predetermined threshold for the one of theplurality of sub-drives, the method includes re-mapping a superblockfrom the one of the plurality of sub-drives to another of the pluralityof sub-drives based on a current data temperature of the superblockindependently of any garbage collection operation.

According to another aspect, a non-volatile memory system is disclosed.The non-volatile memory system may include a non-volatile memory havinga plurality of sub-drives, as well as a controller in communication withthe plurality of sub-drives. The controller may be configured to sortdata associated with a host write command, as the data is received froma host, into one of the plurality of sub-drives based on a determineddata temperature of the data associated with the host write command. Thecontroller may be further configured to sort data, already stored in afirst sub-drive of the plurality of sub-drives, into a differentsub-drive of the plurality of sub-drives by logically remapping aportion of the data already stored in the first sub-drive, withoutrewriting the portion of the data into a different physical location,independently of any garbage collection operation in the firstsub-drive.

In a further aspect, a method is disclosed for managing data in anon-volatile memory system having a plurality of sub-drives and acontroller in communication with the sub-drives. The method may includethe controller receiving a host data write at the memory system anddirecting the host data write to one of the plurality of sub-drivesbased on a first sorting technique. The method may also include thecontroller determining whether an amount of valid data in one of theplurality of sub-drives exceeds a predetermined amount of a logicaladdress space for the one of the plurality of sub-drives. When theamount of valid data in the one of the plurality of sub-drives exceedsthe predetermined amount, the method includes re-mapping a superblockfrom the one of the plurality of sub-drives to another of the pluralityof sub-drives, without rewriting any data from the superblock to anotherphysical location, based on a current data temperature of thesuperblock.

Separately or in combination with the above-noted method, a method forinitially sorting data in a non-volatile memory system is described. Themethod may be executed in a non-volatile memory system with a pluralityof sub-drives each associated with a different data temperature range.The controller of the system may maintain a list of most recent hostdata writes for one of the plurality of sub-drives. The method mayinclude comparing the logical addresses of data in a received host writecommand to logical addresses of data in the list of most recent hostdata writes for the one of the plurality of sub-drives. When a logicaladdress of data in the received host data write is present in the list,the method includes automatically routing the data in the received hostwrite command to a different one of the plurality of sub-drivesassociated with a hotter data temperature range than the one of theplurality of sub-drives.

Referring now to FIG. 1A, a block diagram illustrating a non-volatilememory system is shown. The non-volatile memory (NVM) system 100includes a controller 102 and non-volatile memory that may be made up ofone or more non-volatile memory die 104. As used herein, the term dierefers to the set of non-volatile memory cells, and associated circuitryfor managing the physical operation of those non-volatile memory cells,that are formed on a single semiconductor substrate. Controller 102interfaces with a host system and transmits command sequences for read,program, and erase operations to non-volatile memory die 104.

The controller 102 (which may be a flash memory controller) can take theform of processing circuitry, one or more microprocessors or processors(also referred to herein as central processing units (CPUs)), and acomputer-readable medium that stores computer-readable program code(e.g., software or firmware) executable by the (micro)processors, logicgates, switches, an application specific integrated circuit (ASIC), aprogrammable logic controller, and an embedded microcontroller, forexample. The controller 102 can be configured with hardware and/orfirmware to perform the various functions described below and shown inthe flow diagrams. Also, some of the components shown as being internalto the controller can also be stored external to the controller, andother components can be used. Additionally, the phrase “operatively incommunication with” could mean directly in communication with orindirectly (wired or wireless) in communication with through one or morecomponents, which may or may not be shown or described herein.

As used herein, a flash memory controller is a device that manages datastored on flash memory and communicates with a host, such as a computeror electronic device. A flash memory controller can have variousfunctionality in addition to the specific functionality describedherein. For example, the flash memory controller can format the flashmemory to ensure the memory is operating properly, map out bad flashmemory cells, and allocate spare cells to be substituted for futurefailed cells. Some part of the spare cells can be used to hold firmwareto operate the flash memory controller and implement other features. Inoperation, when a host needs to read data from or write data to theflash memory, it will communicate with the flash memory controller. Ifthe host provides a logical address to which data is to be read/written,the flash memory controller can convert the logical address receivedfrom the host to a physical address in the flash memory. The flashmemory controller can also perform various memory management functions,such as, but not limited to, wear leveling (distributing writes to avoidwearing out specific blocks of memory that would otherwise be repeatedlywritten to) and garbage collection (after a block is full, moving onlythe valid pages of data to a new block, so the full block can be erasedand reused).

Non-volatile memory die 104 may include any suitable non-volatilestorage medium, including NAND flash memory cells and/or NOR flashmemory cells. The memory cells can take the form of solid-state (e.g.,flash) memory cells and can be one-time programmable, few-timeprogrammable, or many-time programmable. The memory cells can also besingle-level cells (SLC), multiple-level cells (MLC), triple-level cells(TLC), or use other memory cell level technologies, now known or laterdeveloped. Also, the memory cells can be fabricated in a two-dimensionalor three-dimensional fashion.

The interface between controller 102 and non-volatile memory die 104 maybe any suitable flash interface, such as Toggle Mode 200, 400, or 800.In one embodiment, memory system 100 may be a card based system, such asa secure digital (SD) or a micro secure digital (micro-SD) card. In analternate embodiment, memory system 100 may be part of an embeddedmemory system.

Although in the example illustrated in FIG. 1A NVM system 100 includes asingle channel between controller 102 and non-volatile memory die 104,the subject matter described herein is not limited to having a singlememory channel. For example, in some NAND memory system architectures,such as in FIGS. 1B and 1C, 2, 4, 8 or more NAND channels may existbetween the controller and the NAND memory device, depending oncontroller capabilities. In any of the embodiments described herein,more than a single channel may exist between the controller and thememory die, even if a single channel is shown in the drawings.

FIG. 1B illustrates a storage module 200 that includes plural NVMsystems 100. As such, storage module 200 may include a storagecontroller 202 that interfaces with a host and with storage system 204,which includes a plurality of NVM systems 100. The interface betweenstorage controller 202 and NVM systems 100 may be a bus interface, suchas a serial advanced technology attachment (SATA) or peripheralcomponent interface express (PCIe) interface. Storage module 200, in oneembodiment, may be a solid state drive (SSD), such as found in portablecomputing devices, such as laptop computers, and tablet computers.

FIG. 1C is a block diagram illustrating a hierarchical storage system. Ahierarchical storage system 210 includes a plurality of storagecontrollers 202, each of which controls a respective storage system 204.Host systems 212 may access memories within the hierarchical storagesystem via a bus interface. In one embodiment, the bus interface may bea non-volatile memory express (NVMe) or a fiber channel over Ethernet(FCoE) interface. In one embodiment, the system illustrated in FIG. 1Cmay be a rack mountable mass storage system that is accessible bymultiple host computers, such as would be found in a data center orother location where mass storage is needed.

FIG. 2A is a block diagram illustrating exemplary components ofcontroller 102 in more detail. Controller 102 includes a front endmodule 108 that interfaces with a host, a back end module 110 thatinterfaces with the one or more non-volatile memory die 104, and variousother modules that perform functions which will now be described indetail. A module may take the form of a packaged functional hardwareunit designed for use with other components, a portion of a program code(e.g., software or firmware) executable by a (micro)processor orprocessing circuitry that usually performs a particular function ofrelated functions, or a self-contained hardware or software componentthat interfaces with a larger system, for example.

Modules of the controller 102 may include a sub-drive data routingmodule 112 present on the die of the controller 102. As described below,the sub-drive data routing module 112 may provide functionality forrouting data from a host only to a particular portion of non-volatilememory 104 and for moving data at predetermined times between variousportions of the non-volatile memory 104 based on a frequency of hostactivity regarding the data. The sub-drive data routing module 112 ofthe controller 102 may accomplish this by tracking activity (e.g. thenumber of host writes or the number of host reads) to individual logicalblock addresses (LBAs) in predefined sections of contiguous LBAs,referred to herein as LBA blocks, in the logical address space. Thesub-drive data routing module 112 may then assign an average activitycount, also referred to herein as temperature, to all the LBAs includedin that particular LBA block and, upon initiation of a garbagecollection operation in a sub-drive, move data associated with aparticular LBA to a physical block in the same or another sub-drivebased on the temperature associated with that LBA. The sub-drive datarouting module 112 may also manage sub-drives differently in the NVMsystem 100 such that only one sub-drive includes an open host writeblock, thus is the only sub-drive accepting host data from the host.Also, all other sub-drives, except for the single sub-drive that acceptshost data, include open relocation blocks for accepting data relocatedfrom a garbage collection operation. In other words, in oneimplementation all data from the host must always first go to the singlesub-drive dedicated to receive host data and all other sub-drives onlyreceive relocated data from each other or the single dedicated sub-drive(referred to herein as a staging sub-drive).

A buffer manager/bus controller 114 manages buffers in random accessmemory (RAM) 116 and controls the internal bus arbitration of controller102. A read only memory (ROM) 118 stores system boot code. Althoughillustrated in FIG. 2A as located separately from the controller 102, inother embodiments one or both of the RAM 116 and ROM 118 may be locatedwithin the controller 102. In yet other embodiments, portions of RAM 116and ROM 118 may be located both within the controller 102 and outsidethe controller. Further, in some implementations, the controller 102,RAM 116, and ROM 118 may be located on separate semiconductor die.

The RAM 116 in the NVM system 100, whether outside the controller 102,inside the controller or present both outside and inside the controller102, may contain a number of items, including a copy of one or morepieces of the logical-to-physical mapping tables for the NVM system 100.The RAM 116 may contain block activity data 117 that is used to trackthe temperature of data in the various sub-drives. The block activitydata may be maintained at different levels of granularity, for exampleon a superblock level, in the form of individual LBA counters (orcounters for the average temperature/activity for larger groups of LBAs)and so on. The RAM 116 may also include a free block list 121 indicatingcurrently unused physical superblocks available for use in any of thesub-drives of the non-volatile memory 104.

Front end module 108 includes a host interface 120 and a physical layerinterface (PHY) 122 that provide the electrical interface with the hostor next level storage controller. The choice of the type of hostinterface 120 can depend on the type of memory being used. Examples ofhost interfaces 120 include, but are not limited to, SATA, SATA Express,SAS, Fibre Channel, USB, PCIe, and NVMe. The host interface 120typically facilitates transfer for data, control signals, and timingsignals.

Back end module 110 includes an error correction controller (ECC) engine124 that encodes the data bytes received from the host, and decodes anderror corrects the data bytes read from the non-volatile memory. Acommand sequencer 126 generates command sequences, such as program anderase command sequences, to be transmitted to non-volatile memory die104. A RAID (Redundant Array of Independent Drives) module 128 managesgeneration of RAID parity and recovery of failed data. The RAID paritymay be used as an additional level of integrity protection for the databeing written into the NVM system 100. In some cases, the RAID module128 may be a part of the ECC engine 124. A memory interface 130 providesthe command sequences to non-volatile memory die 104 and receives statusinformation from non-volatile memory die 104. In one embodiment, memoryinterface 130 may be a double data rate (DDR) interface, such as aToggle Mode 200, 400, or 800 interface. A flash control layer 132controls the overall operation of back end module 110.

Additional components of NVM system 100 illustrated in FIG. 2A includethe media management layer 138, which performs wear leveling of memorycells of non-volatile memory die 104 and manages mapping tables andlogical-to-physical mapping or reading tasks. NVM system 100 alsoincludes other discrete components 140, such as external electricalinterfaces, external RAM, resistors, capacitors, or other componentsthat may interface with controller 102. In alternative embodiments, oneor more of the physical layer interface 122, RAID module 128, mediamanagement layer 138 and buffer management/bus controller 114 areoptional components that are not necessary in the controller 102.

FIG. 2B is a block diagram illustrating exemplary components ofnon-volatile memory die 104 in more detail. Non-volatile memory die 104includes peripheral circuitry 141 and non-volatile memory array 142.Non-volatile memory array 142 includes the non-volatile memory cellsused to store data and includes address decoders 148, 150. Thenon-volatile memory cells may be any suitable non-volatile memory cells,including NAND flash memory cells and/or NOR flash memory cells in atwo-dimensional and/or three-dimensional configuration. Peripheralcircuitry 141 includes a state machine 152 that provides statusinformation to controller 102. Non-volatile memory die 104 furtherincludes a data cache 156 that caches data being read from or programmedinto the non-volatile memory cells of the non-volatile memory array 142.The data cache 156 comprises sets of data latches 158 for each bit ofdata in a memory page of the non-volatile memory array 142. Thus, eachset of data latches 158 may be a page in width and a plurality of setsof data latches 158 may be included in the data cache 156. For example,for a non-volatile memory array 142 arranged to store n bits per page,each set of data latches 158 may include N data latches where each datalatch can store 1 bit of data.

In one implementation, an individual data latch may be a circuit thathas two stable states and can store 1 bit of data, such as a set/reset,or SR, latch constructed from NAND gates. The data latches 158 mayfunction as a type of volatile memory that only retains data whilepowered on. Any of a number of known types of data latch circuits may beused for the data latches in each set of data latches 158. Eachnon-volatile memory die 104 may have its own sets of data latches 158and a non-volatile memory array 142. Peripheral circuitry 141 includes astate machine 152 that provides status information to controller 102.Peripheral circuitry 141 may also include additional input/outputcircuitry that may be used by the controller 102 to transfer data to andfrom the latches 158, as well as an array of sense modules operating inparallel to sense the current in each non-volatile memory cell of a pageof memory cells in the non-volatile memory array 142. Each sense modulemay include a sense amplifier to detect whether a conduction current ofa memory cell in communication with a respective sense module is aboveor below a reference level.

The non-volatile flash memory array 142 in the non-volatile memory 104may be arranged in blocks of memory cells. A block of memory cells isthe unit of erase, i.e., the smallest number of memory cells that arephysically erasable together. For increased parallelism, however, theblocks may be operated in larger metablock units. One block from each ofat least two planes of memory cells may be logically linked together toform a metablock. Referring to FIG. 3 , a conceptual illustration of arepresentative flash memory cell array is shown. Four planes orsub-arrays 300, 302, 304 and 306 of memory cells may be on a singleintegrated memory cell chip, on two chips (two of the planes on eachchip) or on four separate chips. The specific arrangement is notimportant to the discussion below and other numbers of planes may existin a system. The planes are individually divided into blocks of memorycells shown in FIG. 3 by rectangles, such as blocks 308, 310, 312 and314, located in respective planes 300, 302, 304 and 306. There may bedozens or hundreds of blocks in each plane. Blocks may be logicallylinked together to form a metablock that may be erased as a single unit.For example, blocks 308, 310, 312 and 314 may form a first metablock316. The blocks used to form a metablock need not be restricted to thesame relative locations within their respective planes, as is shown inthe second metablock 318 made up of blocks 320, 322, 324 and 326.

The individual blocks are in turn divided for operational purposes intopages of memory cells, as illustrated in FIG. 4 . The memory cells ofeach of blocks 308, 310, 312 and 314, for example, are each divided intoeight pages P0-P7. Alternately, there may be 16, 32 or more pages ofmemory cells within each block. A page is the unit of data programmingwithin a block, containing the minimum amount of data that areprogrammed at one time. The minimum unit of data that can be read at onetime may be less than a page. A metapage 400 is illustrated in FIG. 4 asformed of one physical page for each of the four blocks 308, 310, 312and 314. The metapage 400 includes the page P2 in each of the fourblocks but the pages of a metapage need not necessarily have the samerelative position within each of the blocks. A metapage is typically themaximum unit of programming, although larger groupings may beprogrammed. The blocks disclosed in FIGS. 3-4 are referred to herein asphysical blocks because they relate to groups of physical memory cellsas discussed above. As used herein, a logical block is a virtual unit ofaddress space defined to have the same size as a physical block. Eachlogical block may include a range of logical block addresses (LBAs) thatare associated with data received from a host. The LBAs are then mappedto one or more physical blocks in the non-volatile memory system 100where the data is physically stored.

The term superblock may be used interchangeably with the term metablockherein. A superblock, as described in more detail below with referenceto FIG. 5 , is a metablock that assigns one of the constituent blocks tocontain exclusively metadata regarding parity information for all of theremaining constituent blocks of the metablock. For example, each page ofthe designated parity block of a superblock may contain exclusive (XOR)data of the user data in a page of the remaining blocks of thesuperblock. The block in the superblock designated to contain paritydata is typically the last block, but any block may be used in otherimplementations. Additionally, a superblock may span multiple dies, forexample as many as 64 dies or higher.

Referring to FIG. 5 , an example of a superblock 500 and its componentparts is shown. As noted previously, a superblock 500 may be a fixednumber of physical blocks 502 of data as well as one block 504 thatcontains exclusive or (XOR) data for every page of every other block 502in the superblock 500. Each block 502 is comprised of a plurality ofpages 506 that includes a plurality of pieces 508 of data. Each datapiece 508 is an amount of data, for example a 4 Kbytes piece of data,that is associated with a logical block address (LBA). The LBAs shown inthe example data pieces 508 of FIG. 5 are simply provided by way ofexample to show a situation where the data pieces 508 in a page 506 areassociated with discontinuous LBAs.

In FIG. 6 , a conceptual illustration of the non-volatile memory 600(corresponding to non-volatile memory 104 in FIGS. 2A-2B) is shown. Thenon-volatile memory 600 is divided into sub-drives for storing data,including sub-drives 604, 606, 608 configured to store data associatedwith LBAs determined to have particular “temperatures.” As noted above,the temperatures relate to the frequency with which the data is written.Using a hot/cold sorting function 602 that may be part of the sub-drivedata routing module 112, the controller 102 routes data from hostcommands 610 to a sub-drive.

As noted previously and described in greater detail below, thetemperature of a given LBA refers to the frequency of host activityregarding the LBA associated with the data where, in one implementation,host activity refers only to host write operations. Although in otherimplementations the host read operations may also be considered as hostactivity, the discussion herein focuses on write activity as trackingand utilizing write activity may provide desired write amplificationbenefits. A simplified version of tracking data temperature is describedherein, where temperature may be tracked on a superblock granularitybasis such that all LBAs in a given superblock are given the sametemperature. Other granularities of assigning and tracking temperatureare also contemplated.

As shown in FIG. 6 , data may be sorted into sub-drives each associatedwith a particular temperature threshold or range. The sub-drives 604,606, 608 shown in FIG. 6 include a hot data sub-drive 604, a medium datasub-drive 606 and a cold data sub-drive 608, where the hot datasub-drive 604 is configured to contain only data associated with LBAshaving a high frequency of host activity, the medium data sub-drive 606is configured to store data associated with LBAs of an intermediatelevel of host activity that is less than that of the hot data sub-drive604, and the cold data sub-drive 608 is configured it contain dataassociated with LBAs having infrequent host activity (less than theactivity found in the intermediate data sub-drive 606). Although threesub-drives having data temperature associations are illustrated, anynumber of two or more sub-drives associated with respective temperatureranges are contemplated to allow for different granularity of datasorting by determined data temperature.

Each of the sub-drives 604, 606, 608 is a collection of superblocks thatare managed together. Also, each of the sub-drives 604, 606, 608 mayexist in separate non-volatile memory die 104, the same non-volatilememory die, or each straddle multiple non-volatile memory die 104 in theNVM system 100. Each sub-drive may include only one type of memory cell,such as SLC or MLC, or multiple types of memory cells.

The initial routing of data from the host to the sub-drives and betweensub-drives is managed by the sub-drive data routing module 112 in thecontroller 102. With respect to initial host writes to a sub-drive, anyof a number of hot/cold sorting functions 602 may be implemented. In oneimplementation, the sorting function 602 of the sub-drive data routingmodule 112 is configured such that all data coming from a host writeinto the non-volatile memory 600 is only sent initially to an open hostwrite superblock 603 in the sub-drive that the LBAs of the incoming hostwrite were last written to. If the superblock of incoming data for thehost write includes updated data for LBAs that are currently insuperblocks in different sub-drives, then the incoming superblock ofhost data may be written to the highest temperature sub-drive associatedwith the incoming LBAs. In another implementation, the sorting function602 may cause the controller 102 to direct incoming host writes to anext hottest sub-drive. For example, if the LBAs in the superblock ofthe incoming host write data were previously associated with asuperblock 500 in the cold sub-drive 608, the incoming host write wouldbe directed to the intermediate sub-drive 606.

In other implementations of the hot/cold sorting algorithm 602, allincoming host write data may be written to a dedicated staging sub-drive(not shown) that is not associated with a temperature and from which thehost write data may be remapped into one of the temperature-associatedsub-drives 604, 606, 608. It is also contemplated that all incoming hostdata may initially be written to the hot sub-drive 604. In yet anotherimplementation, the hot/cold sorting function 602 for incoming hostwrites may simply use a round robin technique that takes turns directingsequential superblock host writes to a different sub-drive 604, 606, 608each time. As discussed in greater detail herein, another initial hostsuperblock write routing technique is contemplated, which looks atrecent write density of the LBAs in the superblock, that may react morequickly to changes in the write activity associated with LBAs stored ina particular superblock. Any of a number of other initial host writerouting algorithms are also contemplated.

In one implementation, after data is routed to a desired sub-driveduring the initial host write, valid data from a selected sourcesuperblock is only re-written during a garbage collection operation toan open relocation superblock 605 into the same sub-drive as the sourcesuperblock for that valid data.

Data flow possibilities into and between the sub-drives 604, 606, 608 ofthe non-volatile memory 600 are shown in FIG. 6 for one implementation.Host data writes 610 handled via the hot/cold sorting function 602 ofthe sub-drive data routing module 112 are shown in solid lines, as arethe garbage collection operations where valid data is only written tothe same source sub-drive during garbage collection. The initial hostwrite paths 612 and the garbage collection paths 616 are shown as solidlines because they represent actual data movement to new physicallocations. The various host data write paths 612 illustrated may changedepending on the particular hot/cold sorting function version used, asdescribed above.

In contrast to the solid lines of initial host write paths 612 andgarbage collection paths 616, possible re-mapping paths 614 ofsuperblocks from one sub-drive to another are shown as dotted lines. There-mapping of superblocks between sub-drives is accomplished logically,separately from any garbage collection activity, such that no data isrewritten to different physical locations. This allows the NVM system100 to use separate criteria for re-mapping superblocks to a differenttemperature sub-drive and for selecting a source block for garbagecollection. For example, if temperature sorting was combined withgarbage collection then the sorting may be slowed down by the fact thatthe coldest block in a higher temperature sub-drive that may need to bedemoted from that higher temperature sub-drive to a colder temperaturesub-drive, may not be the same block that is most efficient for purposesof garbage collection from the sub-drive. So, if the superblock with theleast amount of valid data (typically selected for a garbage collectionoperation) does not coincide with the coldest superblock in thatsub-drive, then the hot/cold data sorting by garbage collection may beless accurate. The re-mapping of superblocks may be triggered by one ofthe sub-drives overflowing its allotted logical address space and thecontroller 102 may select a coldest block for re-mapping to the nextcolder sub-drive (or hottest block for re-mapping to the next hotterdrive, for example if the cold sub-drive 608 is too full) and re-mapthat superblock into the other sub-drive.

Referring to FIG. 7 , a version of a non-volatile memory 700corresponding to the non-volatile memory 600 of FIG. 6 is shown with apredetermined logical space capacity assigned to each sub-drive (in thisexample, 5% for the hot sub-drive 704, 15% for the intermediatesub-drive 706 and 80% of the logical address space allocated to the coldsub-drive 708). The predetermined logical space refers to a percentageamount of the total address space of the NVM system 100 and not to anyspecific LBAs or LBA ranges in that address space. Accordingly, are-mapping trigger for remapping one or more superblocks to a differentsub-drive may be based on a sub-drive receiving data in a host writethat pushes the total logical address space contained in the sub-driveabove the respective predetermined amount of the address space allottedto that sub-drive. Other fixed percentages of logical space allocationbesides the 5%/15%/80% example provided may be implemented. The amountof logical space allocation for the sub-drives may be variable in otherimplementations, where there may be an algorithm implemented in thecontroller 102 for providing a dynamic amount of logical space in thesub-drives based on work load or other factors that may affect there-mapping of superblocks. For simplicity, it is assumed in the exampleof FIG. 7 that the amount of logical space allocated to each sub-driveis some fixed amount.

Also illustrated in FIG. 7 is a hypothetical non-uniform workload ofincoming host writes where the hot, intermediate and cold sub-drives704, 706, 708 are each receiving a different percentage (in thisexample, 50%, 30% and 20% respectively) of the total host writes. It isgenerally expected that the workload for each sub-drive will vary,particularly when looking at the distribution of host write activityamong the sub-drives over shorter snapshots of time. The controller 102may track the number of host writes of LBAs in each superblock 500 in asub-drive over time.

The boundaries of the temperature ranges assigned to the sub-drives,such as the hot, medium and cold sub-drives in the examples of FIG. 6 ,may be set to predetermined values at the time of manufacture or thecontroller 102 may use an adaptive algorithm to search for optimizedtemperature ranges to assign to each sub-drive 604, 606, 608 based onobserved data temperature distributions. When a re-mapping of asuperblock to a different sub-drive is necessitated by a sub-driveoverflowing its predetermined amount of the NVM system's 100 logicaladdress space, then the coldest superblock may be selected from thesub-drive and re-mapped logically to the next colder sub-drive. In otherimplementations, in situations where the sub-drive that is overflowingits predetermined logical amount of space is the coldest sub-drive thehottest superblock may be selected and logically re-mapped into the nexthotter sub-drive.

Any of a number of different data temperature tracking mechanisms may beused to monitor the temperature of data written into the sub-drives ofthe NVM system 100. Two different data temperature tracking mechanismsthat track data temperature at the superblock level are illustrated inFIGS. 8A-8C. FIG. 8A shows a sample data temperature tracking mechanismwhere the time that a superblock is first closed (completely written)from a host write operation is tracked in an ordered list 800.Superblock order in the list 800 would then approximately correspond tothe order data was written by the host, with the most recent hostwritten superblock being identified in the left-most entry of the list800 and the oldest superblock being represented by the last superblockentry on the opposite end of the list in FIG. 8A. In the data agetracking version of FIG. 8A, any garbage collection destinationsuperblock (D) would inherit the position of the last source block (S)from which valid data was copied. Thus, because valid data from severalsource superblocks in a sub-drive is typically needed to fill up thedestination superblock D in that same sub-drive, the destinationsuperblock D would inherit the position in the list 800 of the lastsource superblock S copied from and the positions of the earlier sourcesuperblocks for that destination superblock would not be taken intoaccount.

FIG. 8B illustrates a data age list 802 for a slightly different versionof a data age tracking mechanism. In the version of FIG. 8B, each entrytracks the order of closing of superblocks without maintaining aconnection to just host write operations as described in FIG. 8A.Instead, the method of FIG. 8B is a simplified method that simply looksat the time any block was closed and puts the most recently closedsuperblock at the beginning (here, the left side) of the list 802regardless of whether it was a host write or a garbage collection write.When a destination superblock D is closed in this version, it will looknew data and be placed at the beginning of the list. The version of FIG.8B may lead to cold data taking a longer time to reach the older (andthus colder) end of the list. The data age list versions of FIGS. 8A and8B are generated for each sub-drive separately. FIG. 8C shows a legendexplaining the list entry types for the lists 800, 802 of FIGS. 8A and8B.

In one implementation, the controller 102, via the sub-drive datarouting module 112, keeps track of all host write transactions for everyLBA in every superblock for the life of the NVM system 100. Thesub-drive data routing module 112 may store this information in theblock activity data 117 maintained in RAM 116. Thus, the predeterminedamount of time within which the number of host writes to an LBA aretracked may be the entire life of the NVM system 100 and a workload forthe sub-drives may be based on the percentage of the total host writesto LBAs in each particular sub-drive. In other implementations, in orderto provide a more useful indication of changes in host write density toLBAs and the associated sub-drives containing those LBAs, thepredetermined amount of time may refer to a fixed-size window of timethat extends back a limited amount of time to the present, wherein onlythe most recent host writes are included in the workload calculation andearlier LBA hits are removed from the respective counters.

A visual representation of this sliding window of time within which thehost write activity at LBAs is shown in FIGS. 9A and 9B. In FIG. 9A, theincoming host data stream 900 is represented as predetermined amounts ofhost data, shown as host data chunks 902, that are accumulated overtime. The host data chunk size may be a fixed and constant amount in oneimplementation, for example the host data chunk size may be in theincrement of a superblock 500. The controller 102 may look only at theLBA hit rate (in terms of density, or hit rate per LBA) in a slidingwindow 904 of time, where the time may be represented by the number ofconsecutive host data chunks 902 from the most recent to a predeterminednumber of host data chunks prior in time. Within this window 904, all ofthe host transactions for LBAs are tallied and the sub-drives notedwithin which data associated with the LBAs currently reside, and apercentage workload of the amount of LBA hits in the time window for aparticular sub-drive may be determined. As shown in FIG. 9B, when a nexthost data chunk 902 has been accumulated, the window 904 slides toinclude the latest host data chunk 902 and the oldest host data chunk902 previously in the window is removed, representing that the LBAtransaction counts associated with that now excluded host data chunk 902are subtracted from the respective workload calculation. In this manner,the current workload of LBAs in the various sub-drives may moreaccurately be reflected and older activity at LBAs is removed. The abovetechnique and system for tracking and updating (host write activity) forLBA blocks is just one example and other LBA write density and sub-driveworkload tracking and update methods are contemplated.

A method of utilizing the NVM system 100 with sub-drives and datastructures described above is illustrated in FIG. 10 . Referring to FIG.10 , a flow chart describing an implementation of the data flow insub-drives 604, 606, 608 the non-volatile memory 600 is described. Datais received at the NVM system 100 associated with a host write command(at 1002). The sub-drive data routing module 112 of the controller 102may use an incoming hot/cold sort function 602 to initially direct thehost write to a desired sub-drive (at 1002). As noted above, thetechnique for the initial host write sort may be any of a number ofexisting techniques, including always writing the incoming data into ahottest sub-drive, always writing incoming data into a next hottersub-drive than a current sub-drive containing the LBA now beingoverwritten and so on.

Periodically, for example after every host write to the NVM system 100,the controller 102 may determine whether a garbage collection operationis needed for any of the sub-drives (at 1006). One suitable garbagecollection trigger may be the number of free blocks in the free blockpool shared by the sub-drives in the non-volatile memory 104 fallingbelow a predetermined minimum value. If the controller 102 detects thattoo few free blocks are available based on the free block list 121, thena garbage collection operation may be initiated. The number of freeblocks is just one example of a garbage collection trigger and differentor additional garbage collection triggers are contemplated.

Once triggered, the sub-drive in the non-volatile memory 104 is selectedfrom which a source superblock will be garbage collected (at 1008). Onesub-drive selection process, based on selecting the sub-drive thatcurrently has an amount of over-provisioning (OP) that is the most overits calculated targeted OP amount, is described in greater detail below.Once the sub-drive is selected, the a source superblock is selected fromthat sub-drive (1010), for example the superblock 500 having the leastamount of valid data. Valid data from the selected source superblock isthen copied to a destination (relocation) superblock in the samesub-drive (at 1012). As noted previously, the valid data copied from asource superblock is only copied into another superblock in the samesub-drive and no data crosses sub-drive boundaries during garbagecollection. The sorting of previously written data from one sub-drive toa different sub-drive based on data temperature happens separately in alogical re-mapping process described below. After all valid data piecesfrom the selected source superblock 500 have been relocated, then theselected source superblock may be added to the free block list 121maintained in RAM 116 (at 1014). Superblocks 500 in the free block list121 may be later used in any of the sub-drives as needed.

Referring again to FIG. 10 , if garbage collection is not needed after aparticular host write (at 1006), or if garbage collection is performedas described above, the sub-drive data routing module 112 alsodetermines whether a logical re-mapping of a superblock is needed. Forexample, the sub-drive data routing module may determine if a sub-driveis too full because it now contains more valid data than itspredetermined amount of logical address space the logical address spacesize that it was assigned (at 1016). If no sub-drive has overflowed itspredetermined portion of the NVM system 100 logical address space, thenthe process of receiving and processing host write data may continue (at1016, 1002). If a sub-drive has overflowed its predetermined amount oflogical address space, then a superblock in that identified sub-drive islogically re-mapped to a different sub-drive to re-balance the logicalspace distribution (at 1018, 1020).

In one implementation, the superblock selected for logical re-mappingfrom the sub-drive identified as being over its allotted logical addressamount may be the coldest superblock in that sub-drive and may bere-mapped to the next coldest sub-drive as illustrated in FIG. 7 . Inother implementations, the superblock selected for remapping to adifferent sub-drive due to logical address space overflow in aparticular sub-drive may be the hottest block and the sub-drive to whichthat superblock is remapped may then be the next hotter sub-drive (e.g.from SD2 to SD1 in FIG. 7 ). The coldest (or hottest) superblock in asub-drive may be selected according to any method being used to trackthe temperature of data in the sub-drives, such as the closed block agelists (800, 802) of the different superblock age tracking methodsdescribed above with respect to FIG. 8A or 8B.

Referring again to the garbage collection decision path of FIG. 10 , andthe step of selecting a sub-drive from which to garbage collect asuperblock, the decision as to which particular sub-drive 604, 606, 608requires a garbage collection operation may be based on targetover-provisioning thresholds for each of the different sub-drives.Overprovisioning, as used herein, refers to the amount of physical spacein non-volatile memory greater than the amount of logical address space.The total amount of overprovisioning for the entire non-volatile memory104 may be preset at manufacture and, based on current host accessdensity (also referred to herein as data temperature), such as writeactivity, may be distributed among the sub-drives as respective targetoverprovisioning thresholds.

The target overprovisioning thresholds for each sub-drive in thenon-volatile memory, as described in greater detail below, aredetermined based on the current logical capacity occupied by valid datain each sub-drive and the current write traffic (also referred to hereinas workload) in each sub-drive. The NVM system 100, through thesevariable target overprovisioning settings, takes advantage of thepattern of data movement between sub-drives driven by the datatemperature boundaries assigned the sub-drives to help avoid writeamplification for “hotter” (higher update frequency) data. For example,the NVM system 100 may be configured at manufacture to include apredetermined amount of minimum physical capacity overprovisioning forthe system as a whole and then divide up the logical capacity as desiredamong the sub-drives where a sub-drive associated with a data typehaving a higher likelihood of update is allocated a larger capacityoverprovisioning than a sub-drive associated with a data type having alower frequency of update.

As noted above, the non-volatile memory 104 of the NVM system 100, as awhole, may be manufactured with an overprovisioning amount such thatthere is a predetermined extra physical capacity (e.g., extra physicalsuperblocks) greater than the predetermined total logical capacity. Eachsub-drive in the NVM system 100 possesses a variable portion of the NVMsystem's logical capacity based on the historical flow of data into eachsub-drive based on predetermined. Also, for a given window of time, suchas window 904 (FIG. 9 ) that is based on a most recent set of datachunks 902 received, a percentage workload (W) may be determined foreach sub-drive. The workload is a measurement of host access density toLBAs (e.g. the host write activity directed to LBAs) in the sub-drives.In one implementation, workload may be defined as the total number ofhits (e.g. write operations) at each LBA in a sub-drive over adesignated window time period and the percentage workload for asub-drive is that total number of hits divided by all hits at any LBA inthe whole NVM system during the window 904.

Based on the current logical capacity, current workload and the totaloverprovisioning of the entire NVM system, the controller 102 via thesub-drive routing module 112 can then calculate a targetover-provisioning to optimize the physical overcapacity for eachsub-drive. Finally, by selecting a superblock for garbage collectionfrom a sub-drive that currently is above its respective calculatedtarget overprovisioning amount, the overprovisioning can be adjusted.Thus, the overprovisioning of each sub-drive may be determined based onthe workflow (i.e., access density in terms of the number of hostwrites) and selection of a superblock for a garbage collection operationmay be made based on the relative overprovisioning status of eachsub-drive.

FIG. 11 illustrates a process for selecting a source superblock for agarbage collection operation after a garbage collection trigger has beendetected. The current workload for each sub-drive is calculated over thepredefined window 904 by the controller 102 (at 1102). The sub-drivedata routing module may then determine the actual amount ofoverprovisioning already present in each sub-drive (at 1104), forexample by looking at the amount of physical space already associatedwith each sub-drive relative to the amount of valid data present in thesub-drive. A target over-provisioning desired for each sub-drive may becalculated based on that determined workload in each sub-drive (at1106). Once the target overprovisioning is calculated from the workload,the sub-drive data routing module may then identify the sub-drive havinga current over-provisioning level that is the greatest amount over itscalculated target OP level (at 1108). A superblock is then selected fromthat identified sub-drive for garbage collection (at 1110). The criteriafor superblock selection may be any of a number of criteria, such as thesuperblock with the least amount of valid data, the most recentlywritten superblock, or other criteria.

Any of a number of target overprovisioning formulas and techniques maybe used to determine target overprovisioning for each sub-drive.

One suitable algorithm may be:

$\theta_{i} = \sqrt{\frac{\alpha_{i} \cdot v_{i}}{\left( {\sum\limits_{i}\sqrt{\alpha_{i} \cdot v_{i}}} \right)^{2}}}$where θ, is the fraction (0 to 1) of target OP that should be applied tosub-drive i; α_(i) is the fraction (0 to 1) of total NVM system validlogical space in sub-drive i; and v_(i) is the fraction (0 to 1) oftotal host write workload W attributed to sub-drive i. In the examplesof FIGS. 6-7 , the number of sub-drives is 3 and so i=3. The host writeworkload W distribution may be calculated over some sliding window oftime as discussed above. Any of a number of different approaches andformulas for determining the target OP may be used. Additional detailson known forms of target OP calculations may be found in, for example,U.S. Pat. No. 9,021,231, the entirety of which is hereby incorporatedherein by reference.

Additionally, a somewhat cruder, more iterative “hit or miss” method ofdetermining desired overprovisioning for each of the sub-drives may beimplemented based on an analysis of a write amplification surfacegenerated for the NVM system. An example of a standard writeamplification algorithm is

${WriteAmplification} = {\sum\limits_{k = 0}^{n}{{{GroupHitRate}\left( {SD}_{k} \right)}{{WriteAmp}\left( {OP}_{SD_{k}} \right)}}}$where a write amplification surface may be generated as the iterativesum of each of k sub-drives (SD) group hit rate multiplied by the writeamplification for that sub-drive at a given overprovisioning levelWriteAmp(OP_(SD) _(k) ). One such write amplification surface 1502calculated using the standard write amplification algorithm above isprovided in FIG. 15 , where different target overprovisioning levels forone sub-drive may be iterated to determine overprovisioning levels forthe other sub-drives that hit or closely approach the theoreticalminimum 1504 of the write amplification surface 1502. The theoreticalminimum 1504 is the optimum write amplification point. In the example ofFIG. 15 , assuming a 10% total net overprovisioning for the entirememory system and a predetermined workload, the optimal writeamplification point may be 1.8% of the overprovisioning (OP) allocatedto sub-drive A, 3.5% allocated to sub-drive B, and 4.7% allocated tosub-drive C.Initial Host Write With Hot Host List

A method of sorting initially written host data to a desired sub-drivebased on data temperature is illustrated in FIG. 12 . The method may beexecuted in a system such as illustrated in FIGS. 6-7 and utilized in anoverall data management flow at step 1004 of FIG. 10 . To implement thisparticular host write sort method, the hot/cold sorting function 602 ofthe sub-drive routing module 112 may look at recent host write densityto react to changing host write workload patterns and reduce writeamplification through better initial assignment of data to anappropriate sub-drive during a host write.

The method includes keeping a separate first in first out (FIFO) recentwrite list of superblocks for each sub-drive other than the hottestsub-drive. Referring to the three sub-drive non-volatile memory 104version of FIG. 12 , the controller 102 maintains a hot host list forthe intermediate temperature sub-drive and for the cold sub-drive. Thehot host lists may be maintained as separate lists in RAM 116. The hothost lists (HHL1 and HHL2) may each have a fixed length of only a lastpredetermined number of writes to the respective sub-drive SD1, SD2 suchthat, when the list length is filled to its maximum length with recentwrites, a next write to the list pushes the oldest write off of thelist.

The initial host write sort may reduce the endurance penalty due toinaccuracies of hot/cold data copies while not requiring a lot of systemresources. It is based on indirect measurement of host write densityusing block-level algorithm with adjustable accuracy-speed ratio asillustrated in FIG. 13 .

Referring to FIGS. 12 and 14 , the initial host write sorting method mayinclude maintaining a FIFO (first in first out) list of recentlywritten, by host writes, superblocks for each sub-drive other than thehottest sub-drive (at 1402). The number of recent host superblock writestracked for each sub-drive SD1, SD2 may be the same number of blocksHHL1 for SD1, HHL2 for SD2. It is assumed that a hit of an LBA withinthe relatively small number of HHL1 or HHL2 recently written blocks is astrong indicator of higher write density per unit, and is used totrigger re-mapping of an LBA to a hotter sub-drive in certaincircumstances. If a new host write comes in and invalidates an LBAcurrently stored in any of the blocks that are on the FIFO lists HHL1,HHL2 (at 1404), the new data is not written in the open block in thatsub-drive but instead is written the next hottest one, for example fromSD1 to SD0, or from SD2 to SD1 (at 1406). In contrast, if the new hostwrite does not invalidate an LBA in one of the host hot lists (at 1404),then the incoming data may be written to the sub-drive that already hasthe LBA in it (at 1408). After a new host write to a superblock occurs,whether it hits on LBAs in a superblock already on the list or not, thenew superblock write is added to the appropriate hot host list in thesub-drive written to (at 1410). If the hot host list is already full,then the oldest of the recent host writes to that sub-drive on thesub-drive's hot host list is dropped off of the list.

Eventually, the new hot data being remapped, for example from SD1 toSD0, triggers remapping of one of the oldest block from SD0 to SD1 (seedashed lines between SD0 and SD1 in FIG. 12 representing re-mappingflows). The re-mapping may be triggered, as discussed in FIG. 10 , dueto overflow of the proportion of logical address space allotted to SD0.Thus, the coldest superblock in SD0 is no longer considered ‘hot’,regardless of amount of obsolete data in it, and this re-mapping makessure that no stale colder data is stuck in SD0. Remapping to a coldersub-drive is done logically, without a reclaim (garbage collection)copy, as discussed above.

If the workload pattern changes so that host write ‘hot spot’ moves toanother set of LBAs, the data remapping from sub-drive to sub-drive willhappen as soon as the host writes the hot data twice, in cases where thesecond host write to the LBA happens within the fixed number of writestracked in HHL1 or HHL2, while cold data will get re-mapped to a colderSD. In other embodiments, a host hot lists (HHL1 and HHL2) may alsoinclude a super-block written by garbage collection and not just hostwrites if there are not enough blocks written by the host or/and thereare GC blocks containing relatively recently written data (for example,when the superblocks on the HHLs are garbage collected and thus thegarbage collection superblocks contain hot data). Ordering within thelist would maintain the order to keep the block in approximate order oftime since written by the host. For example, in one implementation wherethe HHLs include garbage collection activity as well as host writes, theHHL may be the left-most entries (e.g. most recent 4 entries) of thedata age lists 800 or 802 of FIG. 8A or 8B used for a particularsub-drive.

Referring to FIG. 13 , a hypothetical probability ratio between datagroups in a NVM system 100, assuming the workload and capacitydistribution of FIG. 12 , is shown. The plot 1300 in FIG. 13 is builtusing Poisson function as an approximation to Binomial distribution. Ifthe workload pattern is stable, like in workload pattern of FIG. 12 ,such as an enterprise SSD workload standard suggested by the JEDEC SolidState Technology Association of Arlington, Va., the ‘noise’ remappingfrom sub-drive to sub-drive may be minimized, as most data fromdifferent temperature groups may be distinguishable due to write densityper unit being used as an indicator (40:5:1 ratio in JEDEC) instead ofprior methods of using the probability of data group hit (only 5:3:2ratio in JEDEC). The diagram shows difference in accuracy of separatinghot data from medium, and medium from cold.

The left-most points of the plot in FIG. 13 , where HHL1 size is thelower (hot/medium) trace 1304 and the HHL2 size is the upper(medium/cold) trace 1302, is at the point equivalent to 0.01 DW (1% ofdrive capacity written). In this case, the probability of a host writehitting an LBA within the HHL1 and HHL2 FIFO lists is close to writedensity per unit (40:5:1 ratio in JEDEC). The right-most point of theplot in FIG. 13 illustrates a hypothetical large HHL1 and HHL2 size(containing up to the full list of superblocks of the sub-drive),equivalent to 1 to 5 DWs, as typical time between writes. In this case,the probability of host write may be close to the probability of thedata group hit (only 5:3:2 ratio in JEDEC).

Although the initial host write sorting method of FIGS. 12-14 aredescribed in the context of working with the specific data managementprocess of FIG. 10 , the method and system of FIGS. 12-14 may be usedindependently from the techniques of FIG. 10 and instead may be usedalone or in combination with other sub-drive data management systems andtechniques. FIG. 13 also shows hypothetical cases of setting the size ofthe HHLs (HHL1 for SD1 and HHL2 for SD2 in the example of FIG. 12 )larger or smaller and the associated tradeoffs. in the first case 1306,where the lengths HHLs are smaller, the expected accuracy of hot andcold data sorting using the methods described herein is expected to behigher, but proceed at a slower pace than the second case 1308, wherethe HHL sizes are shown as larger. The two HHL cases 1306, 1308 areillustrated for the particular logical sub-drive sizing and workloaddistribution of the example of FIG. 12 , and assume a specific number ofsuperblocks (SBs), however these cases 1306 and 1308 are simply providedby way of example and other sub-drive sizes, superblock numbers, andworkload distributions are also contemplated.

In the present application, semiconductor memory devices such as thosedescribed in the present application may include volatile memorydevices, such as dynamic random access memory (“DRAM”) or static randomaccess memory (“SRAM”) devices, non-volatile memory devices, such asresistive random access memory (“ReRAM”), electrically erasableprogrammable read only memory (“EEPROM”), flash memory (which can alsobe considered a subset of EEPROM), ferroelectric random access memory(“FRAM”), and magnetoresistive random access memory (“MRAM”), and othersemiconductor elements capable of storing information. Each type ofmemory device may have different configurations. For example, flashmemory devices may be configured in a NAND or a NOR configuration.

The memory devices can be formed from passive and/or active elements, inany combinations. By way of non-limiting example, passive semiconductormemory elements include ReRAM device elements, which in some embodimentsinclude a resistivity switching storage element, such as an anti-fuse,phase change material, etc., and optionally a steering element, such asa diode, etc. Further by way of non-limiting example, activesemiconductor memory elements include EEPROM and flash memory deviceelements, which in some embodiments include elements containing a chargestorage region, such as a floating gate, conductive nanoparticles, or acharge storage dielectric material.

Multiple memory elements may be configured so that they are connected inseries or so that each element is individually accessible. By way ofnon-limiting example, flash memory devices in a NAND configuration (NANDmemory) typically contain memory elements connected in series. A NANDmemory array may be configured so that the array is composed of multiplestrings of memory in which a string is composed of multiple memoryelements sharing a single bit line and accessed as a group.Alternatively, memory elements may be configured so that each element isindividually accessible, e.g., a NOR memory array. NAND and NOR memoryconfigurations are exemplary, and memory elements may be otherwiseconfigured.

The semiconductor memory elements located within and/or over a substratemay be arranged in two or three dimensions, such as a two-dimensionalmemory structure or a three-dimensional memory structure.

In a two dimensional memory structure, the semiconductor memory elementsare arranged in a single plane or a single memory device level.Typically, in a two-dimensional memory structure, memory elements arearranged in a plane (e.g., in an x-z direction plane) which extendssubstantially parallel to a major surface of a substrate that supportsthe memory elements. The substrate may be a wafer over or in which thelayer of the memory elements are formed or it may be a carrier substratewhich is attached to the memory elements after they are formed. As anon-limiting example, the substrate may include a semiconductor such assilicon.

The memory elements may be arranged in the single memory device level inan ordered array, such as in a plurality of rows and/or columns.However, the memory elements may be arrayed in non-regular ornon-orthogonal configurations. The memory elements may each have two ormore electrodes or contact lines, such as bit lines and word lines.

A three-dimensional memory array is arranged so that memory elementsoccupy multiple planes or multiple memory device levels, thereby forminga structure in three dimensions (i.e., in the x, y and z directions,where the y direction is substantially perpendicular and the x and zdirections are substantially parallel to the major surface of thesubstrate).

As a non-limiting example, a three-dimensional memory structure may bevertically arranged as a stack of multiple two dimensional memory devicelevels. As another non-limiting example, a three-dimensional memoryarray may be arranged as multiple vertical columns (e.g., columnsextending substantially perpendicular to the major surface of thesubstrate, i.e., in the y direction) with each column having multiplememory elements in each column. The columns may be arranged in a twodimensional configuration, e.g., in an x-z plane, resulting in a threedimensional arrangement of memory elements with elements on multiplevertically stacked memory planes. Other configurations of memoryelements in three dimensions can also constitute a three-dimensionalmemory array.

By way of non-limiting example, in a three dimensional NAND memoryarray, the memory elements may be coupled together to form a NAND stringwithin a single horizontal (e.g., x-z) memory device levels.Alternatively, the memory elements may be coupled together to form avertical NAND string that traverses across multiple horizontal memorydevice levels. Other three dimensional configurations can be envisionedwherein some NAND strings contain memory elements in a single memorylevel while other strings contain memory elements which span throughmultiple memory levels. Three dimensional memory arrays may also bedesigned in a NOR configuration and in a ReRAM configuration.

Typically, in a monolithic three dimensional memory array, one or morememory device levels are formed above a single substrate. Optionally,the monolithic three-dimensional memory array may also have one or morememory layers at least partially within the single substrate. As anon-limiting example, the substrate may include a semiconductor such assilicon. In a monolithic three-dimensional array, the layersconstituting each memory device level of the array are typically formedon the layers of the underlying memory device levels of the array.However, layers of adjacent memory device levels of a monolithicthree-dimensional memory array may be shared or have intervening layersbetween memory device levels.

Then again, two-dimensional arrays may be formed separately and thenpackaged together to form a non-monolithic memory device having multiplelayers of memory. For example, non-monolithic stacked memories can beconstructed by forming memory levels on separate substrates and thenstacking the memory levels atop each other. The substrates may bethinned or removed from the memory device levels before stacking, but asthe memory device levels are initially formed over separate substrates,the resulting memory arrays are not monolithic three dimensional memoryarrays. Further, multiple two dimensional memory arrays or threedimensional memory arrays (monolithic or non-monolithic) may be formedon separate chips and then packaged together to form a stacked-chipmemory device.

Associated circuitry is typically required for operation of the memoryelements and for communication with the memory elements. As non-limitingexamples, memory devices may have circuitry used for controlling anddriving memory elements to accomplish functions such as programming andreading. This associated circuitry may be on the same substrate as thememory elements and/or on a separate substrate. For example, acontroller for memory read-write operations may be located on a separatecontroller chip and/or on the same substrate as the memory elements.

One of skill in the art will recognize that this invention is notlimited to the two-dimensional and three-dimensional exemplarystructures described but cover all relevant memory structures within thespirit and scope of the invention as described herein and as understoodby one of skill in the art.

Methods and systems have been disclosed for managing received data in amultiple sub-drive non-volatile memory system. The data may be managedthrough a direct write process where data is routed through an initialsorting algorithm to sub-drives in non-volatile memory and subsequentsorting of data and garbage collection operations in the non-volatilememory are performed independently of one another. Separately, or incombination with the independent garbage collection and logical sortingof superblocks of data, a method of initially sorting host write datainto sub-drives based on a write density temperature measurement isdisclosed. The systems and methods may permit reduction of writeamplification, and thus overall improvement of IOPS, for a non-volatilememory system.

It is intended that the foregoing detailed description be understood asan illustration of selected forms that the invention can take and not asa definition of the invention. It is only the following claims,including all equivalents, that are intended to define the scope of theclaimed invention. Finally, it should be noted that any aspect of any ofthe preferred embodiments described herein can be used alone or incombination with one another.

We claim:
 1. A storage system, comprising: storage memory havingsub-drives, the sub-drives comprising a first sub-drive and a secondsub-drive; one or more controllers configured to cause: providing anidentification of one or more recently written superblocks for the firstsub-drive; receiving a first data from a host write; and when the hostwrite invalidates a logical block address associated with the one ormore recently written superblocks for the first sub-drive: writing thefirst data into the second sub-drive that is next hotter than the firstsub-drive; and refraining from writing the first data into an open blockin the first sub-drive.
 2. The storage system of claim 1, wherein theone or more controllers are configured to cause: when the host writedoes not invalidate the logical block address associated with the one ormore recently written superblocks for the first sub-drive, writing thefirst data into the open block in the first sub-drive, wherein the firstsub-drive includes a block corresponding to the logical block address.3. The storage system of claim 2, wherein providing the identificationof the one or more recently written superblocks for the first sub-drivecomprises providing the identification for only a predetermined numberof the one or more recently written superblocks for the first sub-drive,and wherein the one or more controllers are configured to cause:updating the identification of the one or more recently writtensuperblocks for the first sub-drive when the first data is written intothe open block of the first sub-drive; and when a quantity of the one ormore recently written superblocks exceeds the predetermined number,removing an identification of an oldest recently written superblock forthe first sub-drive from the identification of the one or more recentlywritten superblocks for the first sub-drive.
 4. The storage system ofclaim 1, wherein the one or more controllers are configured to cause:moving data previously stored in the first sub-drive into a differentsub-drive of the storage memory by re-mapping at least a portion of thedata previously stored in the first sub-drive, without rewriting the atleast a portion of the data previously stored in the first sub-drive,into a different physical location of the storage memory.
 5. The storagesystem of claim 4, wherein moving the data previously stored in thefirst sub-drive comprises moving the data previously stored in the firstsub-drive into the different sub-drive of the storage memory,independently of any garbage collection operation in the firstsub-drive.
 6. The storage system of claim 4, wherein: the at least aportion of the data previously stored in the first sub-drive comprises asuperblock of the first sub-drive; the different sub-drive comprises anext colder sub-drive of the sub-drives, wherein the next coldersub-drive comprises a sub-drive associated with data having a datatemperature less than a data temperature of data associated with thefirst sub-drive; and re-mapping the at least a portion of the datapreviously stored in the first sub-drive comprises selecting a coldestsuperblock of the first sub-drive and re-mapping the coldest superblockto the different sub-drive.
 7. The storage system of claim 4, wherein:the at least a portion of the data previously stored in the firstsub-drive comprises a superblock of the first sub-drive; the differentsub-drive comprises a next hotter sub-drive of the sub-drives, whereinthe next hotter sub-drive comprises a sub-drive associated with datahaving a data temperature greater than a data temperature of dataassociated with the first sub-drive; and re-mapping the at least aportion of the data previously stored in the first sub-drive comprisesselecting a hottest superblock of the first sub-drive and re-mapping thehottest superblock to the different sub-drive.
 8. The storage system ofclaim 1, comprising: an open block group, comprising superblocksassignable to any of the sub-drives for data storage, wherein the one ormore controllers are configured to cause: initiating a garbagecollection operation in one of the sub-drives in response to detectingthat an amount of the superblocks in the open block group is below apredetermined minimum threshold; and selecting a source superblock forthe garbage collection operation from a sub-drive having an amount ofoverprovisioning that is greater than a target overprovisioning for thesub-drive.
 9. The storage system of claim 1, wherein the one or morecontrollers are configured to cause: when valid data is relocated duringa garbage collection operation, relocating the valid data only within asame sub-drive of the storage memory.
 10. The storage system of claim 1,wherein the one or more controllers are configured to cause: re-mappingat least a portion of data stored in the first sub-drive when an amountof valid data in the first sub-drive exceeds a predetermined amount oflogical address space assigned to the first sub-drive.
 11. A method fora storage system, the method comprising: providing an identification ofone or more recently written superblocks for a first sub-drive ofstorage memory; receiving a first data from a host write; and when thehost write invalidates a logical block address associated with the oneor more recently written superblocks for the first sub-drive: writingthe first data into a second sub-drive that is next hotter than thefirst sub-drive; and refraining from writing the first data into an openblock in the first sub-drive.
 12. The method of claim 11, comprising:when the host write does not invalidate the logical block addressassociated with the one or more recently written superblocks for thefirst sub-drive, writing the first data into the open block in the firstsub-drive, wherein the first sub-drive includes a block corresponding tothe logical block address.
 13. The method of claim 11, comprising:moving data previously stored in the first sub-drive into a differentsub-drive of the storage memory by re-mapping at least a portion of thedata previously stored in the first sub-drive, without rewriting the atleast a portion of the data previously stored in the first sub-drive,into a different physical location of the storage memory.
 14. The methodof claim 13, wherein moving the data previously stored in the firstsub-drive comprises moving the data previously stored in the firstsub-drive into the different sub-drive of the storage memory,independently of any garbage collection operation in the firstsub-drive.
 15. The method of claim 11, wherein: the storage memorycomprises an open block group, the open block group comprisingsuperblocks assignable to any of sub-drives of the storage memory; andthe method comprises: initiating a garbage collection operation in oneof the sub-drives in response to detecting that an amount of thesuperblocks in the open block group is below a predetermined minimumthreshold; and selecting a source superblock for the garbage collectionoperation from a sub-drive of the storage memory having an amount ofoverprovisioning that is greater than a target overprovisioning for thesub-drive.
 16. The method of claim 11, comprising: when valid data isrelocated during a garbage collection operation, relocating the validdata only within a same sub-drive of the storage memory.
 17. The methodof claim 11, comprising: re-mapping at least a portion of data stored inthe first sub-drive when an amount of valid data in the first sub-driveexceeds a predetermined amount of logical address space assigned to thefirst sub-drive.
 18. An apparatus, comprising: means for providing anidentification of one or more recently written superblocks for a firstsub-drive of storage memory; means for receiving a first data from ahost write; and when the host write invalidates a logical block addressassociated with the one or more recently written superblocks for thefirst sub-drive: means for writing the first data into a secondsub-drive that is next hotter than the first sub-drive; and means forrefraining from writing the first data into an open block in the firstsub-drive.
 19. The apparatus of claim 18, comprising: when the hostwrite does not invalidate the logical block address associated with theone or more recently written superblocks for the first sub-drive, meansfor writing the first data into the open block in the first sub-drive,wherein the first sub-drive includes a block corresponding to thelogical block address.
 20. The apparatus of claim 18, comprising: meansfor moving data previously stored in the first sub-drive into adifferent sub-drive of the storage memory, wherein the means for movingcomprises means for re-mapping at least a portion of the data previouslystored in the first sub-drive, without rewriting the at least a portionof the data previously stored in the first sub-drive, into a differentphysical location of the storage memory.